Subject: * DLS (clarifications)

From: [email-masked] (Shekar Nair)
Date: Mon, 3 May 93 11:09:37 PDT

Having just joined this discussion, I would appreciate clarifications
on DLS. If my Questions seem silly kindly ignore them.

1. Why does DLS use TCP as the transport mechanism ?

Is not the overhead of TCP headers costly on the WAN ?. Multiplexing
multiple LLC connections over a TCP connection could temporarily freeze
all LLC connections during TCP error recovery process due to a loss of
a single frame.
Is there any flaw in using a `smart LLC2` logic over the wide area that
can provide re-sequencing support over the WAN ?. By using this approach
the WAN overhead could be minimized, at the same time SNA frames could
be transported reliably.

Is connectivity to a DLS capable 6611 router the major issue ?
Have other alternatives been considered ?

2. What is the scope of DLS ?

Is it not spoofing LLC2 frames to provide reliable SNA/Netbios transport over wide area, and to provide source route termination to enable upto 7 hops on
each side of the WAN ?.

The DLS enhancements (some of them) suggested seem to be overlapping with
APPN functionality, such as Class of service (COS), directory service, transmission groups etc. Does this mean we would have these features duplicated
on APPN + DLS capable routers ?

regards,

Shekar Nair
ascom Timeplex

[email-masked]